Fix KubernetesPodOperator validate xcom json and add retries#32113
Fix KubernetesPodOperator validate xcom json and add retries#32113eladkal merged 5 commits intoapache:mainfrom
Conversation
|
Congratulations on your first Pull Request and welcome to the Apache Airflow community! If you have any issues or are unsure about any anything please check our Contribution Guide (https://github.com/apache/airflow/blob/main/CONTRIBUTING.rst)
|
hussein-awala
left a comment
There was a problem hiding this comment.
Could you follow the steps explained in this doc to activate the pre-commit hooks and fix the static checks?
Then you need to add a test for your change.
db2f6b4 to
7654344
Compare
Thanks will do! Worked on the fixing static checks. Will work on adding tests for the change |
63d8247 to
ca83211
Compare
8ab201c to
aec892d
Compare
|
@jedcunningham can you please review this PR when you have time ? thx! |
389e48b to
6981ab2
Compare
jscheffl
left a comment
There was a problem hiding this comment.
Some comments, mainly related to code style/exception handling
- Added retries to extract_xcom to guard against intermittent network connectivity failures. - xcom json is validated to make sure entire json was retrieved. - xcom sidecar is killed only if xcom json that was retrieved was valid.
05d6324 to
3f797bc
Compare
|
Isn't the description / intenti different now? In the description you write about killing the xcom container only on failure, but seems it is killed always ? |
Yes let me fix the description thank you! |
|
Done fixed the description |
jscheffl
left a comment
There was a problem hiding this comment.
Took a bit of time re-reading the code and first wanted to complain - because the json.loads() looked use-less first hand for me.
PR looks good but still I'd prefer to keep a small additional comment for somebody in future w/o PR context to better understand the logic.
|
Thank you @jens-scheffler-bosch added a comment as per your suggestion |
|
Nice. But now line is too long :). |
|
Fixed long line now ..thx! :-) |
|
Awesome work, congrats on your first merged pull request! You are invited to check our Issue Tracker for additional contributions. |
|
Hello! I am facing this problem. After the fix was merged, did you @aagateuip experience it again? thanks! |
closes: #32111
^ Add meaningful description above
Read the Pull Request Guidelines for more information.
In case of fundamental code changes, an Airflow Improvement Proposal (AIP) is needed.
In case of a new dependency, check compliance with the ASF 3rd Party License Policy.
In case of backwards incompatible changes please leave a note in a newsfragment file, named
{pr_number}.significant.rstor{issue_number}.significant.rst, in newsfragments.